Searching command enhancements

ABSTRACT

A user can access a searching component that allows the user to enter search terms to search for commands associated with a computer program. Some specific embodiments pertain to methods for supporting user access to the searching component, to methods for processing search terms submitted by the user, and to methods for guiding the user in terms of their formulation and selection queries. Methods for generating, organizing and manipulating the search results are also provided.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of and claims priority of U.S.patent application Ser. No. 11/701,125, filed Feb. 1, 2007, which is acontinuation-in-part application of and claims priority to U.S. patentapplication Ser. No. 11/372,545, filed Mar. 10, 2006, now U.S. Pat. No.7,925,975, issued Apr. 12, 2011, the content of which is herebyincorporated by reference in its entirety.

BACKGROUND

A wide variety of different types of computer applications are currentlyin use. Such computer applications often fall into three or moredifferent categories. For instance, rich client applications aretypically applications that run on a client device, such as a desktopcomputer or laptop computer. Other software applications includeweb-based applications in which a client interacts with a web-baseddevice, such as a server using a web browser, in order to run theapplication. Still other software applications include mobile deviceapplications. Mobile device applications might run on mobile devices,such as personal digital assistants (PDAs), telephones, handheldcomputers, etc.

In running a software application, a user typically wishes to performone or more different tasks. As used herein, the term task meansanything that a user wishes to do in the context of a given softwareapplication.

In order to allow users to accomplish the desired tasks, many currentsoftware applications provide a graphical user interface. The userexecutes one or more commands on the graphical user interface toaccomplish a desired task. There are substantially three main ways bywhich people accomplish tasks using a graphical user interface, and theydepend on how frequently the user performs a given task. For tasks thatare performed frequently by the user, the user might learn or memorizethe sequence of steps (or commands) required to perform the task withthe graphical user interface. Also with frequently performed tasks,applications might expose the user interface elements for performing themost popular tasks prominently in the user interface.

A second group of tasks are those that are performed infrequently by theuser. The user may typically browse the menus or tool bars displayed bythe graphical user interface, in order to attempt to locate the userinterface element that can be used to perform the desired task. Anotherway in which users perform infrequent tasks is to seek the help of otherpeople to find out how to perform the task. In doing this, the usermight go to a news group or simply ask another individual how to performthe task.

Finally, when the user does not remember how to perform the task, andcannot find out how to perform the task by asking others, users mighttypically invoke a help mechanism associated with the application. Forinstance, some applications are associated with help documentationstored on a client, or on a web site. The help documentation allows auser to search for a help topic that often explains what to do in orderto accomplish a task that a user wishes to perform.

Of course, there are a number of problems associated with these types ofcurrent systems. Unless the user has the steps for performing a taskmemorized, it can be fairly cumbersome for the user to find out how toperform the task. Asking news groups or physically asking other personshow to perform a task takes a relatively large amount of time and thusreduces efficiency.

In addition, even where the user attempts to hunt through the userinterface to find the user interface element necessary to accomplish thedesired task, the user may encounter problems. For instance, in mostgraphical user interfaces, the features or elements associated with thegraphical user interface are categorized under other elements. In otherwords, the user may go to the “File” drop down menu to look for aparticular feature or element of the graphical user interface. The usermay also go to the “Edit” drop down menu to look for another feature. Ofcourse, if the sought after feature is under an unexpected drop downmenu, this can result in frustration and extra time required for theuser to find that feature.

Similarly, attempting to determine how to perform a task using helpdocumentation often requires a fairly high level of knowledge about thetask. For instance, some help documentation is simply an alphabeticallisting of different tasks. This may be extremely unhelpful to a userwho does not know the technical term for the task to be performed. Byway of example, in one spreadsheet software application, adding rows andcolumns to a spreadsheet is performed using an “insert” command. Ofcourse, it would take a user a fairly long time to track this commanddown, if the user was simply looking under the “add” commands in thehelp documentation.

Similarly, many help mechanisms provide information that is not usefulin a given context. For instance, assume the user is in a wordprocessing application which has no tables in it, but the user wishes toadd a table. The help mechanism might typically be arranged with allinformation related to tables found in a plurality of different spotswithin the help documentation. Thus, the help documentation mightinclude modifying existing tables, adding or deleting rows or columnsfrom tables, and a wide variety of other information dealing withalready-existing tables. Of course, since the user's document has noalready-existing tables, this information is completely useless to theuser. Yet, the user must sift through this information in order toidentify the steps necessary to add a table.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

SUMMARY

A user can access a searching component that allows the user to entersearch terms to search for commands associated with a computer program.Some specific embodiments pertain to methods for supporting user accessto the searching component, to methods for processing search termssubmitted by the user, and to methods for guiding the user in terms oftheir formulation and selection queries. Methods for generating,organizing and manipulating the search results are also provided.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The claimed subject matter is not limited to implementationsthat solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computing environment.

FIG. 2 is a block diagram of a mobile device.

FIG. 3 is a diagrammatic representation of a system within which commandsearching and processing are performed on a client.

FIG. 4 is a flow diagram demonstrating steps associated with operationof the system shown in FIG. 2.

FIG. 4A is a flow diagram illustrating a number of optional steps.

FIGS. 5-9, 10A and 10B are example screenshots demonstrating graphicaluser interfaces.

FIG. 11 is a diagrammatic representation of a system within whichcommand searching and processing are performed on a server.

FIG. 12 is a diagrammatic representation of a system within whichcommand searching and processing are performed on a server that supportsa server-based application.

FIG. 13 is a schematic illustration of an exemplary command searchingand processing component.

FIGS. 14A and 14B are flowcharts demonstrating functionality associatedwith an implementation of an input device access component.

FIG. 14C is a flowchart demonstrating a method for providing a commandsearch index that maps multiple forms of a potential search term to thesame command result.

FIG. 14D is a flowchart demonstrating steps associated with oneimplementation of a rank biasing component.

FIG. 14E is a flowchart demonstrating one implementation of a queryfeedback component.

FIG. 14F is a flowchart demonstrating one implementation of a queryclarification component.

FIG. 14G is a flowchart demonstrating one implementation of a relatedquery component.

FIG. 14H is a flowchart demonstrating one implementation of a resultcategorization component.

FIG. 14I is a flowchart demonstrating one implementation of a titlemanagement component.

FIG. 14J is a flowchart demonstrating one implementation of a slotfilling component 1366.

FIG. 14K is a flowchart demonstrating one implementation of a gallerydisplay component.

FIG. 14L is a flowchart demonstrating one implementation of a dataprovider component.

FIG. 14M is a flowchart demonstrating one implementation of atagging/renaming component.

FIG. 14N is a flowchart demonstrating one implementation of a commandpinning component.

FIGS. 15A, 15B, 16, 17A 17B, 18, and 19 are example screenshotsdemonstrating graphical user interfaces.

DETAILED DESCRIPTION

The present subject matter deals with searching for commands associatedwith software applications, and executing those commands. However,before that subject matter is discussed in more detail, two illustrativecomputing devices will be described.

FIG. 1 illustrates an example of a suitable computing system environment100 on which embodiments may be implemented. The computing systemenvironment 100 is only one example of a suitable computing environmentand is not intended to suggest any limitation as to the scope of use orfunctionality of the claimed subject matter. Neither should thecomputing environment 100 be interpreted as having any dependency orrequirement relating to any one or combination of components illustratedin the exemplary operating environment 100.

Embodiments are operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with various embodimentsinclude, but are not limited to, personal computers, server computers,hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers, telephonysystems, distributed computing environments that include any of theabove systems or devices, and the like.

Embodiments may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Someembodiments are designed to be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules are located in both local and remotecomputer storage media including memory storage devices.

With reference to FIG. 1, an exemplary system for implementing someembodiments includes a general-purpose computing device in the form of acomputer 110. Components of computer 110 may include, but are notlimited to, a processing unit 120, a system memory 130, and a system bus121 that couples various system components including the system memoryto the processing unit 120. The system bus 121 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus.

Computer 110 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 110 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media includes both volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules or other data.Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computer 110. Communication media typicallyembodies computer readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 130 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 131and random access memory (RAM) 132. A basic input/output system 133(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 110, such as during start-up, istypically stored in ROM 131. RAM 132 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 120. By way of example, and notlimitation, FIG. 1 illustrates operating system 134, applicationprograms 135, other program modules 136, and program data 137.

The computer 110 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates a hard disk drive 141 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 151that reads from or writes to a removable, nonvolatile magnetic disk 152,and an optical disk drive 155 that reads from or writes to a removable,nonvolatile optical disk 156 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 141 is typically connectedto the system bus 121 through a non-removable memory interface such asinterface 140, and magnetic disk drive 151 and optical disk drive 155are typically connected to the system bus 121 by a removable memoryinterface, such as interface 150.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 1, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 110. In FIG. 1, for example, hard disk drive 141 is illustratedas storing operating system 144, application programs 145, other programmodules 146, and program data 147. Note that these components can eitherbe the same as or different from operating system 134, applicationprograms 135, other program modules 136, and program data 137. Operatingsystem 144, application programs 145, other program modules 146, andprogram data 147 are given different numbers here to illustrate that, ata minimum, they are different copies.

A user may enter commands and information into the computer 110 throughinput devices such as a keyboard 162, a microphone 163, and a pointingdevice 161, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 120 through a user input interface 160 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A monitor 191 or other type of display device is also connectedto the system bus 121 via an interface, such as a video interface 190.In addition to the monitor, computers may also include other peripheraloutput devices such as speakers 197 and printer 196, which may beconnected through an output peripheral interface 195.

The computer 110 is operated in a networked environment using logicalconnections to one or more remote computers, such as a remote computer180. The remote computer 180 may be a personal computer, a hand-helddevice, a server, a router, a network PC, a peer device or other commonnetwork node, and typically includes many or all of the elementsdescribed above relative to the computer 110. The logical connectionsdepicted in FIG. 1 include a local area network (LAN) 171 and a widearea network (WAN) 173, but may also include other networks. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 110 is connectedto the LAN 171 through a network interface or adapter 170. When used ina WAN networking environment, the computer 110 typically includes amodem 172 or other means for establishing communications over the WAN173, such as the Internet. The modem 172, which may be internal orexternal, may be connected to the system bus 121 via the user inputinterface 160, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 110, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 1 illustrates remoteapplication programs 185 as residing on remote computer 180. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

FIG. 2 is a block diagram of a mobile device 200, which is an exemplarycomputing environment. Mobile device 200 includes a microprocessor 202,memory 204, input/output (I/O) components 206, and a communicationinterface 208 for communicating with remote computers or other mobiledevices. In one embodiment, the afore-mentioned components are coupledfor communication with one another over a suitable bus 210.

Memory 204 is implemented as non-volatile electronic memory such asrandom access memory (RAM) with a battery back-up module (not shown)such that information stored in memory 204 is not lost when the generalpower to mobile device 200 is shut down. A portion of memory 204 isillustratively allocated as addressable memory for program execution,while another portion of memory 204 is illustratively used for storage,such as to simulate storage on a disk drive.

Memory 204 includes an operating system 212, application programs 214 aswell as an object store 216. During operation, operating system 212 isillustratively executed by processor 202 from memory 204. Operatingsystem 212 is illustratively designed for mobile devices, and implementsdatabase features that can be utilized by applications 214 through a setof exposed application programming interfaces and methods. The objectsin object store 216 are maintained by applications 214 and operatingsystem 212, at least partially in response to calls to the exposedapplication programming interfaces and methods.

Communication interface 208 represents numerous devices and technologiesthat allow mobile device 200 to send and receive information. Thedevices include wired and wireless modems, satellite receivers andbroadcast tuners to name a few. Mobile device 200 can also be directlyconnected to a computer to exchange data therewith. In such cases,communication interface 208 can be an infrared transceiver or a serialor parallel communication connection, all of which are capable oftransmitting streaming information.

Input/output components 206 include a variety of input devices such as atouch-sensitive screen, buttons, rollers, and a microphone as well as avariety of output devices including an audio generator, a vibratingdevice, and a display. The devices listed above are by way of exampleand need not all be present on mobile device 200. In addition, otherinput/output devices may be attached to or found with mobile device 200.

FIG. 3 is a block diagram of a computing environment in accordance withan embodiment in which command searching and processing is performed ona client 250. Client 250 is illustratively a desktop computer, a laptopcomputer, or a mobile device, such as a personal digital assistant, atelephone, a handheld computer, etc. In the embodiment shown in FIG. 3,client 250 has a software application 252 thereon which is accessed byuser 254 such that the user can execute one or more commands to performa variety of different tasks. For example, application 252 may be a wordprocessing program, a spreadsheet program, a presentation program, orany other software application that can be accessed by a user 254,though a user interface 271, to perform tasks.

Client 250 is shown with a platform 256. In one embodiment, platform 256is, for example, an operating system that supports a plurality ofdifferent applications 252. In the embodiment shown in FIG. 3, platform256 includes command searching and processing component 258 and commandstore 259. As is described in greater detail below, component 258 isexposed to user 254 through application 252 (or independent ofapplication 252) such that the user can search for commands associatedwith application 252, and optionally execute the desired commands. Inone embodiment, platform 256 exposes an interface 260, such as anapplication programming interface, which can be invoked by application252.

Client 250 is also shown with an optional speech recognition component270. This can be used as described below.

In the embodiment shown in FIG. 3, client 250 is also connected to aserver 262 though a network 264. Network 264 can be any desired network,such as a wide area network, a local area network, etc.

FIG. 4 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 3. FIGS. 3 and 4 will now be described inconjunction with one another. For the purposes of this discussion, it isassumed that user 254 launches application 252 and desires to perform atask using application 252. The user illustratively does not know thecommand or commands required to perform the task. In other words, theuser has not memorized the steps necessary (or the location of the userinterface elements required) to perform the desired task. Therefore,user 254 must locate the command required to perform the desired task.

In accordance with one embodiment, user 254 begins to enter a searchrequest. In one embodiment, user 254 can enter the search requestthrough speech recognition component 270, by simply speaking the desiredsearch request. For purposes of the present discussion, however, it willbe assumed that the user types in the search request one letter at atime, but the invention is not to be so limited.

In any case, FIG. 5 shows one graphical user interface 271 which can beused to receive entry of the search request. User interface 271 in FIG.4 illustrates that application 252 is a presentation program referred toas “Program A”. Command searching and processing component 258 exposestext box 274 through user interface 271 of application 252, to the user.The user can enter a search request, letter by letter, into text box274.

Therefore, after the user 254 types in a first letter in text box 274 onuser interface 271, the letter is transmitted, as a search request 280,to command searching and processing component 258 in platform 256. Inorder to do this, in one embodiment, application 250 provides the searchrequest 280 through the interface 260 exposed by component 258.Receiving the first letter at command searching and processing component258 is indicated by block 299 in FIG. 4.

Component 258 then calculates likely words that complete the letterstring entered thus far. For instance, if the user has typed “ins” themost likely completion of this prefix might be “insert”. This isindicated by block 300 in FIG. 4 and is described in more detail belowwith respect to the example shown in FIG. 5.

In one embodiment, component 258 also receives the context 281 ofapplication 252. For instance, the context will illustratively identifythe particular application 252 for which a command is sought, andprovide an indication of the particular contents of the window currentlyopen and under focus in the application, a position of the cursorrelative to the elements on the open window, etc. Examples of context281 are described in greater detail below and the optional step ofreceiving the context is indicated by block 301 in FIG. 4.

Once the first letter is received, likely completions are calculated,and the context component 258 performs a search through command store259 that stores the commands associated with a plurality of differentapplications. This search is performed based on the received letters,likely completions and the context. Performing the search is indicatedby block 302 in FIG. 4.

In performing the search, component 258 identifies possible commands andcalculates a score indicative of how likely it is that each of thepossible commands is being requested by the user in the search request.This is indicated by block 304 in FIG. 4. While the search can beperformed in any desired way, in one embodiment, the search is performedusing a search engine that is trained with prior probabilities ofcommands.

Once the calculation has been made, component 258 returns the searchresults through interface 260 where they are displayed at user interface271 through application 252. Of course, the results can be returnedwithout going through application 252 as well. In any case, in oneembodiment, component 258 not only displays the most likely commandsgiven the search request, but also displays them in ranked order, giventhe score calculated for each command in block 204. Displaying theranked commands is indicated by block 306 in FIG. 4.

User 254 can then either select one of the displayed commands, orcontinue typing additional letters in the search request. This isindicated by block 308 in FIG. 4. In the embodiment in which the userdoes not select one of the commands, but instead continues to typeletters, processing reverts back to block 302 and another search isperformed, scores are calculated, and the likely commands are againdisplayed in ranked order, as indicated by blocks 304 and 306.

Assume for the sake of the example shown in FIG. 5 that the user 254wishes to insert a table in the particular application 252 which isopen. In the embodiment shown in FIG. 5, user interface 271 shows thatuser 254 has typed into text box 274 the letters “ins”. The context hasalso been provided to component 258. The context indicates, among otherthings, that the open application 252 is a presentation application.Component 258 calculates the probabilities of commands associated withthe input “ins” stored in command store 259. In the particular exampleshown in FIG. 5, component 258 determines that the most probablecompletion of “ins” is “insert”, and component 258 displays, as searchresults, commands which relate to inserting or adding in the givencontext.

It will be noted from this example that component 258 illustratively notonly searches based upon the particular letters input, but based uponsynonyms of the most likely completions of those letters. In otherwords, the most likely completion of the letters “ins” in the presentcontext is “insert”. Therefore, component 258 identifies synonyms for“insert” (such as “add”) and searches for commands that are for“inserting” or “adding” things and that would be most likely, given thecurrent context of the application 252.

As shown in FIG. 5, component 258 returns the search results, rankingthem in order. It can be seen that the first command returned is “insertslide” which is more probable than any of the other commands in thelist. The other commands in the list are rank ordered, according to thescore calculated by component 258 (which can be a likelihood orprobability or other desired measure) and they are numbered, accordingto their rank. In the embodiment shown in FIG. 5, the first nine resultsare number according to their rank, and a plurality of other commandsare also provided, but are not numbered.

The user can select one of the commands from the list of returnedresults 275 by simply clicking on the displayed command. However, in oneembodiment, the user can also select one of the numbered search resultsby simply typing that number in box 274. Any other desired way ofselecting a command from the list 275 can be used as well.

In accordance with the example shown in FIG. 5, the user selects the“insert table” command. Having component 258 receive a command selectionis indicated by block 308 in FIG. 4.

Once the user has selected a command from list 275, if more dialog withthe user is required in order to further refine or disambiguate thecommand, component 258 can conduct that additional dialog. This isdiscussed in greater detail below with respect to FIG. 6. Determiningwhether the extra dialog is required and conducting that dialog isindicated by blocks 310 and 312 in FIG. 4.

Once the dialog is complete, or if no further dialog is required, thatmeans that the selected command has been fully disambiguated bycomponent 258. Component 258 can then either provide additionalinformation to user 254 about the selected command (such as tutorialinformation), or component 258 can simply execute the command selectedby the user. Providing the additional information is described in moredetail below with respect to FIGS. 4A, 8 and 9, and executing theselected command is indicated by block 314 in FIG. 4.

As an example of executing the commands, where the user has selected the“insert table” command, component 258 (after it determines that noadditional dialog is necessary) controls application 252 such thatapplication 252 takes the user to the appropriate place in theapplication to execute the “insert table” command. FIG. 5 displays theappropriate user interface mechanism that allows the user to execute the“insert table” command.

As an example of conducting additional dialog to refine a command,component 258 may conduct a dialog with the user as at block 312 in FIG.4 to determine the size of the table which the user wishes to add.Component 258 then adds it automatically. In another embodiment,component 258 simply allows the user to walk though the “insert table”functionality provided by application 252, once component 258 has takenthe user to that place in the user interface provided by application252.

Also, the additional dialog may further define what the user wishes todo. For example, if the user inputs “delete cell and table”, thecomponent 258 may respond with an inquiry such as “which table” or“which cell”, and then delete the specified table or cell based on theresponse from the user.

In accordance with another embodiment, component 258 (or anothercomponent invoked by component 258) automatically performs the commandselected by the user, receiving user inputs where necessary. Forinstance, user 254 can select the desired user interface elements toinsert a table from the list 275 of possible commands. Component 258 (oranother component invoked by component 258) can then assume control ofapplication 252 and begin to automatically perform that command.However, when it comes to the point where the user interface asks theuser to specify the size of the table (in terms of columns and rows)component 258 simply highlights the field to be modified by the user andpauses until the user has input the desired information and clicked“OK”. In that example, component 258 (or other component) simply waitsuntil the user has selected the desired number of columns and rows andclicked “OK” and component 258 (or other component) then walks theapplication 252 through the remainder of the steps necessary to performthe command of inserting the desired size table within the application,at the specified spot. Automatically executing the command is indicatedby block 314 in FIG. 4.

Of course, if component 258 is not configured to automatically executethe command selected by the user, the user can continue to use component258 as the user is taking the steps to execute the command. Forinstance, if, in FIG. 6, the user again types “ins” into text box 274,component 258 again identifies the possible commands and calculates thescores for the various commands and again displays a list 275 ofpossible commands, given the new context. This is shown in FIG. 7.Specifically, FIG. 7 illustrates that component 258 has now calculatedthe highest scores for the commands of inserting rows and insertingcolumns in a table, because the context indicates that the table hasalready been added as shown in FIGS. 5 and 6.

As briefly mentioned above, component 258 can convey additionalinformation to the user, and not just execute the command. This isindicated in FIG. 4A. For instance, component 258 may illustratively beconfigured to provide user 254 with tutorial information or guided helpin executing the command. In doing so, component 258 first determinesthat it must convey this additional information (e.g., the guided help)to the user as indicated at block 400. The decision to provide theadditional information can be predetermined by the developer, or set bythe user using any desired user interface element, or based on any otherdesired criteria. Component 258 then retrieves and conveys theadditional information, as indicated by block 402. In the embodimentdiscussed herein, the additional information is the guided help ortutorial help, which can be offered to a user in executing a command,and an example of this is illustrated in FIGS. 8 and 9.

For instance, assume for the sake of example that the user types “back”in text box 274 as shown in FIG. 8. Component 258 then calculates themost probable commands, given the input “back” and given the presentcontext and provides the ranked results shown in list 275. FIG. 8 alsoshows that the user has selected the first result in the list (i.e., the“change the background [wizard]” command). The selected command isactually comprised of a command bundle of subcommands that are executedto perform the overall command or task of changing the background.Component 258 then launches the “change background” command bundleassociated with application 252. In the embodiment illustrated, oneexample of the guided help is shown in FIG. 9.

FIG. 9 is a guided help and command interface 500 which not onlyprovides some tutorial information to the user about executing theselected command, but also provides mechanisms by which the user canactually execute the command. For instance, user interface 500 providesa tutorial display portion 502 that displays tutorial content, as wellas a tutorial portion 504 that displays additional tutorial content.User interface 500 also provides command elements 506 that allow a userto select the desired subcommands, within the command bundle, forchanging the background of presentation material provided in application252. The “next” button 506 allows the user to walk through the tutorialand actually execute the command as the user is walking through thetutorial.

From the above discussion, it will be clear that the particular userinterface 271 for conducting command searching can take a wide varietyof different forms. For instance, FIG. 10A shows another embodiment ofuser interface 271. In the embodiment shown in FIG. 10A, the user hasentered “open” in text box 274 and the possible commands are shown inlist 275. The user can ask for additional results using elements 277.

FIG. 10B shows an embodiment of user interface 271 after the user hasselected the “open presentation” command. Component 258 then controlsapplication 252 to bring up the “open” file dialog illustrated in FIG.10B.

From the description thus far, it is clear that the command searchingand processing component 258, and the subject matter related to it, areapplicable not only to rich client applications (such as word processingapplications, spreadsheets, presentation software, etc.) that reside ona client (such as a desktop or laptop computer) but that the subjectmatter is also applicable and useful, in an environment in whichapplication 252 resides on a mobile device, such as a personal digitalassistant, a mobile telephone, a handheld computer, etc. However, FIGS.11 and 12 illustrate that the command searching and processing component258, and the associated subject matter, are also useful in otherenvironments. In one such environment, application 252 resides on aclient, but command searching and processing component 258 residesremotely, such as on a server. In another such environment, application252 and command searching and processing component 258 both resideremotely from the client such as on a server. Items in FIGS. 11 and 12are numbered similarly to corresponding items in FIG. 3.

More specifically, FIG. 11 shows that command searching and processingcomponent 258, and command store 259 are no longer resident on client250. Instead, component 258 resides on server 262, and component 259 isshown coupled to component 258 and can reside at any desirable location.In the embodiment shown in FIG. 11, search request 280 and context 281are provided through platform 256, over network 264, to component 258 onserver 262. Component 258 performs the search, calculates the scoresassociated with the results, and provides the ranked search results backthrough network 264 and platform 256 to application 252, where they areprovided to user 254 through user interface 271.

FIG. 12 is similar to FIG. 11, except that application 252 is now alsolocated on server 262. Therefore, application 252 can be a web-basedapplication which is accessed by client 250 over network 264. In theembodiment shown in FIG. 12, the request and search results aretransmitted back and forth between application 252 and component 258 atserver 262.

It can thus be seen that the present system uses language to findsubstantially any command that a user wishes to execute in anapplication. The user can provide a search request in the user's ownlanguage, and the present system illustratively maps that language tothe correct command by searching based on prior probabilities, givencontext. The commands that are returned are likely the most relevantones for a given search request, in the current context. Commandsreturned, once selected, can be automatically performed for the user, ora user interface can be brought up based on the selected command, awizard can be launched, a rich wizard can be launched, or a tutorial canbe run based on the selected commands.

It should also be noted that the present system pivots functionality ofthe application around the particular command that the user wishes toexecute. For instance, if the user wishes to find all commands in thesystem that have to do with printing, it may be difficult inconventional systems to find those specific commands, because printingcommands are often located in various different user interfacelocations. However, the present component 258 can be used to gather allof that information into a single place, in response to a search requestfor a printing-related command.

A variety of specialized features can be incorporated into the describedcommand searching systems and methods. FIG. 13 is a schematicillustration of a command searching and processing component 258. FIG.13 shows component 258 comprising a variety of different individualcomponents for supporting specialized features. The specialized featuresare illustratively categorized into access support components 1302,command search processing components 1304, post-selection enhancementcomponents 1306, result set features components 1308 and search refiningcomponents 1310. Those skilled in the art will appreciate that all ofthe specialized components illustrated in FIG. 13 are illustrativelyoptional enhancements that may or may not be included in a givenimplementation. Further, the illustrated specialized components need notnecessarily be implemented from within command searching and processingcomponent 258. The illustrated implementation is but one example of howimplementation can be accomplished.

Access support components 1302 include input device access components1350. FIG. 14A is a flowchart demonstrating functionality associatedwith one implementation of an input device access component 1350. Inaccordance with step 1402, a user input is received and is indicative ofcommand search functionality. In accordance with step 1404, the receivedinput is responded to by initiating display of user interface componentsconfigured to support command search functionality. In one embodiment, akey on a keyboard (or a combination of keystrokes) is configured to,upon actuation by a user, initiate display of a user interface componentconfigured for command searching. In one embodiment, the displayedcomponent is a floating user interface that enables a user to search forcommands and then disappears after the command is executed. It should benoted that the present invention is not limited to keyboard-initiatedaccess to command searching components. User-initiated inputs from otherinput devices (e.g., a mouse, a voice-activated command, etc.) canillustratively be configured to initiate a command searching process.Those skilled in the art will understand that inputs from most devicescan be mapped to various functions, which in the present case includesthe command searching functionality.

Command search processing components 1304 include search inputpre-processing components 1352. FIG. 14B is a flowchart demonstratingone implementation of a search input pre-processing component 1352. Inaccordance with step 1406, a command search input is received. Inaccordance with step 1408, the search input is pre-processed in somemanner. Finally, in accordance with step 1410, the pre-processed and/ororiginal search input is included as search terms in the commandsearching process. In one embodiment of the pre-processing step, thereceived command search input (e.g., the words typed into the searchquery area) is evaluated and expanded so that the command search willmatch additional command results. Command search inputs canillustratively be expanded utilizing a variety of techniques such as,but not limited to, synonym generation, morphological transformation ofquery terms (e.g., stemming, etc.), spelling correction, generatingfunctionally equivalent terms, etc.

It should be pointed out that query expansion and other pre-processingare not the only ways to enable a broader and/or more accurate set ofcommand results. FIG. 14C illustrates a method of providing a commandsearch index that maps multiple forms of a potential search term to thesame command result. An example of this is illustrated in the partialscreenshots 15A and 15B. Each of these screenshots shows a set ofcommand search results 1504 that were illustratively returned inresponse to an execution of a command search utilizing a search termshown in box 1502. In FIG. 15A, the search term was “open”. In FIG. 15B,the search term was “opening”. Notably, the result set 1504 is the samein both instances. This outcome is illustratively supported by thesearch input pre-processing components 1352 such as, but not limited to,the methods demonstrated in FIGS. 14B and 14C.

Command search processing components 1304 illustratively include a rankbiasing component 1354. FIG. 14D is a flowchart demonstrating stepsassociated with one implementation of a rank biasing component 1354. Inaccordance with step 1414, a command search input is received. Inaccordance with step 1416, a search process is executed based on thereceived command search input. As is shown in the user interface of FIG.5, command search results can illustratively be ranked within the outputdisplay. In accordance with step 1418, the search results are organizedin the output display based on one or more biasing criteria. As isdemonstrated by block 1420, one example of a biasing criteria is thecommand selection history of one or more users. For example, commandsthat are more frequently utilized by the user that initiated the same(or similar) search can be configured to be more likely to appear higherin the ranking. In addition or alternatively, commands frequently usedby many users in general (e.g., users of the same computing device uponwhich the search is being initiated and/or users of other computingdevices) can be configured for bias toward ranking higher. Those skilledin the art will appreciate that ranking determinations can be configuredto account for a variety of different factors including but not limitedto quality of a match, command selection history, etc.

Search refining components 1310 include query feedback component 1356.FIG. 14E is a flowchart demonstrating one implementation of a queryfeedback component 1356. In accordance with step 1422, a command searchinput is received. In accordance with step 1424, based on the commandsearch input, alternate related queries are determined and presented tothe user. In accordance with step 1426, a selection of one of thealternate queries is received. Finally, in accordance with block 1428, acommand search is executed based on the selected alternate query. In oneembodiment, the alternate queries are simply related optional queries orqueries that may, predictably, simply be of interest to the user (i.e.,determined based on one or more characteristics of their input query).In one embodiment, the alternate queries are options from which the usercan choose to expand or narrow the scope of their search. In oneembodiment, the alternate queries are queries that have proven (e.g.,based on an object criteria such as click patterns, etc.) to be usefulto one or more users that have made the same or similar query. Alternatequeries can be implemented as described for any purpose withoutdeparting from the scope of the present invention.

Search refining components 1310 include query clarification component1358. FIG. 14F is a flowchart demonstrating one implementation of aquery clarification component 1358. In accordance with step 1430, acommand search input is received. In accordance with step 1432, based onthe command search input, the user is presented with a proposedclarification of the input query. In accordance with step 1434, an inputis received from the user in the form of either a conformation of theproposed clarification or a new query that is a version of the firstentered query revised to incorporate the proposed clarification.Finally, in accordance with block 1436, a command search is executedbased on the clarified query (i.e., based on the first entered querymodified either by the user or by the system to reflect the proposedclarification.

An example of this is illustrated in the partial screenshot of FIG. 16.This screenshot shows a user interface illustratively returned inresponse to an execution of a command search utilizing a search termshown in box 1602. In FIG. 16, the search term was “spill.” In response,a proposed query clarification is presented in panel 1604, namely, thesystem asks the user whether the intended query was for “spell” insteadof “spill.” In one embodiment, not by limitation, proposedclarifications are made only when no results (or results believed, basedon an object criteria, to be an unlikely fit for the user'sexpectations) are identified based on the query input by the user.However, this need not necessarily be the case.

As is shown in panel 1606, in addition to presenting a proposedclarified query, the user can be presented with a help option and/or anoption for providing specific or general feedback about the commandsearch system. In one embodiment, feedback provided by the user isutilized as a basis for modification of the command search system usedby the user providing the feedback and/or similar search systemsutilized by others (e.g., the user provides feedback indicating that theterm “spill” should be linked to a particular command . . .subsequently, the user's system and/or the system of another is updatedto include the link). It is to be understood that the help and feedbackfeatures shown in panel 1606 are not limited to being presented to theuser in the context of query clarification. For example, the features ofpanel 1606 can be presented with any query result set, or otherwisepresented to the user.

It should be noted that while the example provided in FIG. 16 is relatedto query clarification the form of a spelling correction this is but oneexample of a query clarification. Those skilled in the art willappreciate that the present invention is not so limited.

Result set features components 1308 include related command component1360. FIG. 14G is a flowchart demonstrating one implementation of arelated query component 1360. In accordance with step 1438, a commandsearch input is received. In accordance with step 1442, based on thecommand search input, a result set (i.e., corresponding to the receivedsearch input) is provided along with one or more alternate queries. Inaccordance with step 1444, a selection indicative of an alternate queryis received. Finally, in accordance with step 1446, another result setis provided but this time the result set is based on the selectedalternate query.

In one embodiment, the alternate queries provided in accordance withstep 1442 are simply related optional queries or queries that may,predictably, simply be of interest to the user (i.e., determined basedon one or more characteristics of their input query). In one embodiment,the alternate queries are options from which the user can choose toexpand or narrow the scope of their search. In one embodiment, thealternate queries are queries that have proven (e.g., based on an objectcriteria such as click patterns, etc.) to be useful to one or more usersthat have made the same or similar query. Alternate queries can beimplemented as described for any purpose without departing from thescope of the present invention.

Result set features components 1362 include result categorizationcomponent 1362. FIG. 14H is a flowchart demonstrating one implementationof a result categorization component 1362. In accordance with step 1448,a command search input is received. In accordance with step 1450, basedon the command search input, search results are determined (i.e.,corresponding to the received search input). In accordance with step1452, the search results are output to the user at least partiallybroken down by category. For example, results related to controls foradjusting text characteristics are identified (i.e., in a user interfacecomponent) as being associated with a first category, while control foradjusting display functions are associated with a second category. Notall search results need necessarily be identified with a category.

Result set features components 1308 include title management component1364. FIG. 14I is a flowchart demonstrating one implementation of atitle management component 1364. In accordance with step 1454, a commandsearch input is received. In accordance with step 1456, based on thecommand search input, a result set (i.e., corresponding to the receivedsearch input) is determined. In accordance with step 1458, the resultset is output to the user in a format that is customized to match thereceived command search input. For example, terminology utilized in theuser input is incorporated into one or more titles output in connectionwith the search results.

An example of this is illustrated in the partial screenshots 17A and17B. Each of these screenshots shows a set of command search results1704 that were illustratively returned in response to an execution of acommand search utilizing a search term shown in box 1702. In FIG. 17A,the search term was “portrait”. In FIG. 17B, the search term was“landscape”. Notably, the result set 1704 includes the same commandresults but the titles in each instance have been altered to reflect theterminology incorporated into the respective box 1702.

Unrelated to title management component 1364, it is worth pointing outthat FIGS. 17A and 17B include a navigation panel 1710. Within panel1710 are “previous” and “next” buttons that enable the user to navigatethrough search results in panel 1704 when not all the results aresimultaneously displayed.

Result set features components 1308 include slot filling component 1364.FIG. 14J is a flowchart demonstrating one implementation of a slotfilling component 1366. In accordance with step 1460, a command searchinput is received. In accordance with step 1462, based on the commandsearch input, the user is presented with a result having control itemfilled in based on information in the received search input. An exampleof this is illustrated in the partial screenshot of FIG. 18. Thisscreenshot shows a user interface illustratively returned in response toan execution of a command search utilizing a search term shown in box1802. In FIG. 18, the search term was “arial.” In response, a fontcontrol menu 1804 is provided with information from the input query(i.e., “arial”) automatically filled in. This is but one of manypotential examples of how slot filling functionality can be implemented.

It should be noted that the present invention is not limited to fillingin a combo box as illustrated in FIG. 18. Other types of controls can beautomatically manipulated as described without departing from the scopeof the present invention. Also, it is part of the present invention toreturn a control menu in response to a command search. That being said,the present invention is not limited to returning a font control menu asshown in FIG. 18. Other control menus can be returned (e.g., in responseto different queries) without departing from the scope of the presentinvention.

Result set features components 1308 include gallery display component1368. FIG. 14K is a flowchart demonstrating one implementation of agallery display component 1368. In accordance with step 1464, a commandsearch input is received. In accordance with step 1466, based on thecommand search input, the user is presented with a result set in agallery format. An example of this is illustrated in the partialscreenshot of FIG. 19. This screenshot shows a user interfaceillustratively returned in response to an execution of a command searchutilizing a search term shown in box 1902. In FIG. 19, the search termwas “math symbol.” In response, a math symbol gallery 1904 is provided.Optional buttons 1906 enable the user to scroll through the gallery(i.e., these button are implemented when fewer than all symbols can besimultaneously displayed).

FIG. 19 is but one of many potential examples of how a gallery displayfunctionality can be implemented in a result set. The present inventionis not limited to returning a match symbol gallery as shown. Othergalleries can be returned (e.g., in response to different queries)without departing from the scope of the present invention.

Result set features components 1308 include data provider component1370. FIG. 14L is a flowchart demonstrating one implementation of a dataprovider component 1366. In accordance with step 1468, a command searchinput is received. In accordance with step 1470, the command searchinput is analyzed and a request for data is identified. In accordancewith step 1472, the requested data is provided as part of search resultsdisplayed to the user in response to the query input. In one example ofthe method of FIG. 14L, a user inputs “show application version.” Thesystem analyzes this query and identifies the fact that the user islooking for information. In response, the system provides the requestedversion information in the area where command search results aretypically displayed. The information may or may not be displayed withsearch results that also match the query input. This is but one exampleof an implementation of the command search functionality to enable auser to request and receive information.

Post-selection enhancement components 1306 include tagging/renamingcomponent 1372. FIG. 14M is a flowchart demonstrating one implementationof a tagging/renaming component 1372. In accordance with step 1474, atag or name is received in relation to a command. In accordance withstep 1476, system parameters are adjusted such that the command willimplement functionality related to the received command or tag. In oneembodiment, in this manner, a user is able to rename a command (e.g., acommand identified by the system as “spelling” can be renamed to “spellchecking”). In another embodiment, in this manner, a user is able toattach a tag to a command (e.g., a user can add a term that will impactwhen the command will be considered matching a given query). It is to beunderstood that the present invention extends to attaching tags orrenaming for any reason.

Post-selection enhancement components 1306 include command pinningcomponent 1374. FIG. 14N is a flowchart demonstrating one implementationof a command pinning component 1374. In accordance with step 1478, arequest to pin is received in relation to a command. In accordance withstep 1480, the system is adjusted as necessary to respond to the requestto pin the identified command. In one embodiment, in this manner, a useris able to add a command from the search result list to a menu, toolbar,quick access toolbar, etc. In one embodiment, in this manner, a user can“click and drag” a command from the search result list so as to create aseparate user interface component in a different location, the separateuser interface component being linked to the associated commandfunctionality.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A method of locating a command to perform adesired task in an application, the method comprising: providing acommand store that contains an indication of commands associated withthe application; receiving a command query; identifying possiblecommands in the command store based on the command query; and returningthe possible commands in a user selectable form such that the possiblecommands can be selected by a user for execution in order to perform thedesired task.
 2. The method of claim 1, further comprising: receiving aninput indicative of a desire to launch a command search user interfacecomponent; responding to the input by initiating a display of thecommand search user interface component; and wherein receiving thecommand query comprises receiving the command query in the form of auser input into the command search user interface component.
 3. Themethod of claim 1, further comprising: receiving an input indicative ofa desire to launch a command search user interface component; respondingto the input by initiating a display of the command search userinterface component; and wherein said returning the possible commandscomprises returning the possible commands within the command search userinterface component.
 4. The method of claim 1, further comprisingterminating display of the command search user interface component inresponse to an additional user input.
 5. The method of claim 1, furthercomprising pre-processing the command query.
 6. The method of claim 1,further comprising providing a command search index that maps multipleforms of a potential command query to the same possible commands in thecommand store.
 7. The method of claim 1, wherein returning the possiblecommands in a user selectable form comprises organizing the possiblecommands based on one or more biasing criteria.
 8. The method of claim1, further comprising presenting the user with an alternate commandquery.
 9. The method of claim 1, further comprising presenting the userwith a proposed query clarification.
 10. The method of claim 1, furthercomprising returning an alternate query in a user selectable componentsuch that the alternate query can be selected by the user for submissionas part of an alternate command search.
 11. The method of claim 1,wherein returning the possible commands further comprises returning thepossible commands organized into groups by category.
 12. The method ofclaim 1, wherein returning the possible commands further comprisesformatting the text of one of the possible commands so as to beconsistent with a characteristic of the command query.
 13. A system forlocating a command to perform a task, the system comprising a searchingcomponent configured to receive a search request, and to identify aplurality of possible commands based on the search request, and toreturn the possible commands in user selectable form, wherein thepossible commands are at least partially broken down by correspondingcategories.
 14. The system of claim 13, wherein the possible commandsreturned in the user selectable form include one possible command havinga rendered appearance that is selected based at least in part on anattribute of the search request.
 15. The system of claim 13, wherein thesearch request is a command search request.
 16. The system of claim 13,wherein the user selectable form is a form from which one of thepossible commands is selectable by a user.
 17. A computer readablemedium storing computer readable instructions which, when executed by acomputer, cause the computer to perform steps of: receiving a commandsearch request; searching a data store to identify a plurality ofpossible commands based on the command search request; and returning alist of the plurality of possible commands as user actuable graphicaluser interface elements, ordered so as to account for at least one rankbiasing factor indicative of the command selection history of one ormore users.
 18. The method of claim 17, wherein the rank biasing factoris indicative of when commands in the list were most recently selected.19. The method of claim 17, wherein the rank biasing factor is a dataitem indicative of a period of, or point in, time.
 20. The method ofclaim 17, wherein the rank biasing factor is indicative of a log of useractivity.